Code rate for control information

ABSTRACT

There is disclosed a method of operating a user equipment in a radio access network. The method includes transmitting feedback control signaling, the feedback control signaling representing a number I of information bits. The I information bits are encoded with a code rate based on a code rate indication. The disclosure also pertains to related devices and methods.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/356,603, filed Mar. 18, 2019, which is a continuation ofInternational Application No. PCT/SE2017/050817, filed Aug. 11, 2017,the entireties of both of which are incorporated herein by reference.

TECHNICAL FIELD

This disclosure pertains to wireless communication technology, inparticular control signaling.

BACKGROUND

Modern wireless communication systems like 5G system, e.g. New Radio(NR), are developed to handle a large variety of use cases, for exampleMobile Broadband (MBB) and low-latency applications. To be able to adaptto highly different demands, new types of control signaling arerequired.

SUMMARY

It is an object of this disclosure to describe approaches allowingimproved and flexible handling of control information, in particular offeedback information, e.g. in uplink or sidelink. The approaches areparticularly advantageously implemented in a 5th Generation (5G)telecommunication network or 5G radio access technology or network(RAT/RAN), in particular according to 3GPP (3^(rd) GenerationPartnership Project, a standardization organization). A suitable RAN mayin particular be a RAN according to NR or LTE Evolution, for examplerelease 15 or later.

Accordingly, there is disclosed a method of operating a radio node, inparticular a user equipment, in a radio access network. The methodcomprises transmitting feedback control signaling, the feedback controlsignaling representing a number I of information bits, wherein the Iinformation bits are encoded with a code rate based on a code rateindication.

Moreover, there is disclosed a radio node, in particular a userequipment, for a radio access network. The user equipment is adapted fortransmitting feedback control signaling, the feedback control signalingrepresenting a number I of information bits, wherein the I informationbits are encoded with a code rate based on a code rate indication. Theradio node or user equipment may comprise, and/or be adapted forutilizing, processing circuitry and/or radio circuitry, in particular atransceiver and/or transmitter, for such transmitting. Alternatively, oradditionally, it may comprise a transmitting module for suchtransmitting. The radio node may be considered a feedbacking radio node,and may in particular be implemented as a user equipment or terminal.However, in some cases, the radio node may be a network node, e.g. inbackhaul communication with another network node like a configuringradio node.

There is also disclosed a method of operating a configuring radio nodein a radio access network. The method comprises configuring afeedbacking radio node, in particular a user equipment, with a code rateindication for feedback control signaling, the code rate indicationindicating a code rate for encoding information bits of the feedbackcontrol signaling. The method may comprise receiving feedback controlsignaling based on the code rate indication and/or the code rate.

Furthermore, a configuring radio node for a radio access network isconsidered. The configuring radio node is adapted for configuring afeedbacking radio node, in particular a user equipment, with a code rateindication for feedback control signaling, the code rate indicationindicating a code rate for encoding information bits of the feedbackcontrol signaling. The configuring radio node may comprise, and/or beadapted for utilizing, processing circuitry and/or radio circuitry, inparticular a transceiver and/or transmitter, for such configuring.Alternatively, or additionally, it may comprise a transmitting modulefor such transmitting. The configuring radio node may be implemented asa network node, in particular a base station like an eNB or gNB, or as auser equipment or terminal, for example in sidelink communication withthe feedbacking radio node, which may also be a user equipment orterminal. In some variants, the configuring radio node may be adaptedfor receiving the feedback control signaling based on the code rateindication and/or the code rate. The node may comprise, and/or beadapted for utilizing, processing circuitry and/or radio circuitry, inparticular a receiver and/or transceiver, and/or a receiving module, forsuch receiving.

Feedback control signaling may comprise feedback control information,which comprise information of different types, e.g. feedback informationand/or acknowledgement information, and/or measurement information(e.g., measurement reporting, and/or channel state or qualityinformation), and/or scheduling request information (e.g., a schedulingrequest), and/or beam information (e.g., beam-specific feedback).Feedback control signaling may be uplink signaling, or sidelinksignaling, or related to backhaul communication. Examples of feedbackcontrol signaling comprise signaling carrying uplink controlinformation, in particular UCI, or signaling carrying sidelink controlinformation, in particular SCI. Feedback control information may pertainto specific signaling received, e.g., feedback information, inparticular acknowledgement information), which may pertain to specificdata streams and/or channels and/or acknowledgement signaling processes.Alternatively, or additionally, feedback control information may pertainto one or more specific channels, in particular physical channels,and/or ports like antenna ports.

The code rate (which may be referred to as coding rate) may generallyindicate or represent a ratio between a number I of information bits(representing control information) and a number E of encoded bits, whichmay be determined based on the information bits, and include and/orrepresent them. Thus, generally, E>I may be considered to hold, andL=E−I may be considered to represent the error coding bits. The Iinformation bits may be jointly encoded, e.g. in one group or insubgroups. Encoding may be considered to comprise error encoding, inparticular error detection coding and/or forward error correctioncoding. Such encoding may add a number of bits to a given number I toenable error detection and/or correction. Different types of errorencoding may be considered, e.g. polar coding or LDPC coding. Note thatdepending on the error encoding type used, the information bits I may beleft untouched, or may be transformed, to be represented in the Eencoded bits. E may be considered to represent the total number of bitsafter encoding, including the representation of the I information bits,plus the error coding bits L, which may be mathematically interwoven.The code rate indication may comprise one or more indicators, which maybe provided or obtained together or separately, e.g. in differentmessages, which may be on the same or different layers, e.g. physicallayer (like DCI signaling), MAC or RRC/RLC layer. Generally, the coderate indication may comprise at least one indicator (e.g., a parameteror index of bit field), which may be provided with a configuration, e.g.via DCI signaling or RRC signaling. The code rate may be determinedbased on the code rate indication, and optionally, be determined basedon one or more additionally indications and/or parameters. The code ratemay, for example, be determined based on the number I, which may bereferred to as payload size (the corresponding information bits may beconsidered the payload) of the feedback control signaling. The feedbackcontrol signaling may be signaling that has been transmitted based onmodulating the encoded bits, e.g. based on an MCS scheme, and/or mappingof modulated symbols/bits in frequency domain and/or time domain, e.g.to subcarriers and/or symbols of resources scheduled or allocated forthe feedback control signaling. Such resources may be scheduled e.g.with a scheduling assignment, and/or other control signaling, which mayindicate which resources are to be used for feedback signalingpertaining to reception of signaling, which may be signaling indicatedby the scheduling assignment. Signaling the feedback signaling pertainsto may generally be communicating signaling and/or reference signaling,which the feedbacking radio node may be scheduled and/or configuredand/or intended to receive. The code rate may for example be determinedbased on bandwidth for feedback control signaling and/or modulationscheme and/or number of information bits and/or encoding scheme and/orthe code rate indication. Transmitting feedback control signaling maycomprise determining the code rate, e.g., directly from the code rateindication, and/or calculating and/or estimating and/or reading it.However, transmitting feedback control signaling with the indicated coderate may be performed without explicitly determining the code rate.Thus, the code rate may be implicit to the feedback control signaling,e.g. represented by the ratio I/E and/or other parameters of thesignaling. Generally, the code rate indication may be implicit orexplicit. Configuring a feedbacking radio node with a code rateindication may be based on and/or comprise determining, implicitly orexplicitly, the code rate. The indicated code rate may be an actual coderate, or an estimate or representation of an actual code rate, e.g. anupper or lower limit representation. Information bits I may beconsidered to be (en-)coded with a code rate R, if I/E=R, or I/Ecorresponds to a representation and/or estimate and/or upper or lowerlimiting representation or R.

The approaches described herein allow flexible adaption of feedbackcontrol signaling to operational conditions. For example, with anindication of a low code rate, a high level of reliability of thefeedback control signaling may be achieved, for example a lowblock-error rate (BLER).

The code rate indication may generally indicate a bandwidth for thefeedback signaling. The bandwidth may for example be indicated as,and/or may represent, a number of subcarriers and/or a number ofresource blocks, e.g. physical or virtual resource blocks. A resourceblock may be considered to represent a number F of subcarriers infrequency domain, e.g. F=12. Alternatively, or additionally, a code rateindication may indicate a mapping between the number I of informationbits and/or payload size (and/or the information bits), and a bandwidthand/or allocated bandwidth or frequency resources, which may beallocated/scheduled for the feedback control signaling.

It may be considered that the code rate indication may indicate one coderate of a set of code rates for a bandwidth. For example, the indicationmay indicate the number of coding bits, and/or the number of encodedbits, and/or the code rate implicitly or explicitly. The set of coderates may comprise a plurality of code rates, which may be code ratesavailable or possible for the bandwidth. The set may be predefinedand/or configured or configurable. For different coding schemes and/ornumber of information bits (or payload size) and/or different types ofinformation for the feedback control signaling, different sets may beprovided, e.g. configured and/or predefined.

In some variants, the code rate and/or the code rate indication may bedetermined (e.g., by the configuring radio node and/or the feedbackingradio node) based on a transmission mode or transmission moderepresentation, e.g. of signaling to which the feedback controlsignaling pertains, and/or may be indicated by a representation orindication thereof. A transmission mode or corresponding representationmay be represented by, and/or pertain to one or more characteristics orparameters, e.g. the MCS to be used, e.g. in the context of linkadaptation, and/or the targeted BLER, and/or Quality of Service, and/orpriority, and/or urgency/latency, and/or the channel on which thefeedback control signaling is to be transmitted (and/or the format ofsuch a channel, e.g. PUCCH format), and/or the channel of signaling thefeedback control signaling pertains to, e.g. provides feedback for, oris determined in response to receiving the channel or signaling. Atransmission mode or its representation may for example indicate whichuplink or sidelink channel the feedback control signaling is to betransmitted on, which in particular may be a physical control channel,e.g. a physical uplink control channel or a physical sidelink controlchannel. Examples of a physical uplink control channel comprise a PUCCH,a short PUCCH, a long PUCCH, a channel for carrying HARQ information, acontrol channel associated to URLLC communication, or similar. Forsidelink, analogous channels may be considered. In another additional oralternative example, the transmission mode or its representation mayindicate the type of feedback control information or signaling, e.g.whether it is acknowledgement signaling (e.g., ACK/NACK) or measurementreporting or scheduling request information or beam-related information.Alternatively, or additionally, a transmission mode or itsrepresentation may pertain to received signaling, and/or a channel ofreceived signaling, the feedback control signaling pertains to (providesfeedback for), e.g. reference signaling on a port or associated to abeam, or to a data channel, which may carry communication signaling,e.g. a dedicated or shared channel, which may be a physical channel likea physical downlink or sidelink shared channel like a PDSCH or PSSCH.The transmission mode may be indicated by the code rate indication. Atransmission mode or its representation may pertain to one or more suchcharacteristics or parameters for the feedback control signaling and/orsignaling the feedback control signaling pertains to. There maygenerally be considered that one or more sets of code rates are provided(e.g., configured or configurable, and/or predefined) for one or moresuch transmission modes and/or characteristics. A code rate indicationmay indicate the set and/or the code rate from the set to be used forthe feedback control signaling.

The code rate indication may indicate an anchor frequency resourcestructure and/or indicating a bandwidth, and/or a bandwidth location ordistribution, for the feedback control signaling. A bandwidth mayindicate a number of subcarriers and/or resource blocks. A bandwidthlocation and/or distribution may indicate where in frequency domain thesubcarriers and/or resource blocks of the bandwidth are located. Thecode rate indication may configure the feedbacking radio node formapping the information bits I, respectively the encoded bits E, to thebandwidth and/or the frequency location or distribution. A frequencydistribution may be contiguous, or distributed in separated,non-neighboring (in frequency domain) frequency intervals, e.g.subcarrier or subcarrier groupings or resource blocks. Non-contiguousfrequency distributions may for example be used in the context offrequency hopping. An anchor frequency resource structure may indicate aresource structure indicating a location of a bandwidth or bandwidthdistribution in frequency domain. An anchor frequency resource structuremay for example be an anchor resource block, whose location may beindicated, and which indicates the location of one or more otherresource blocks relative to the anchor resource block.

The code rate indication may indicate one of a plurality of code ratespossible for a coding scheme. For each coding scheme (e.g., polar codingor LDPC or turbo coding or Reed-Mueller coding), there may be a set ofcode rates available, e.g. predefined and/or configured or configurable,which may be considered possible code rates. The set may comprise aplurality of rates. It may be considered that the code rate to be usedmay be indicated and/or indexed by the code rate indication. The codingscheme may generally be determined based on I, and/or the payload sizeof the feedback control signaling. The code rate may be determinedand/or indicated based on the code rate indication and the codingscheme.

It may generally be considered that the code rate indication indicatesone of a plurality of code rates possible for I information bits. A setof code rates for I information bits and/or based on the payload sizemay be configured or configurable or predefined, which may be consideredthe possible codes rates. The set may comprise a plurality of coderates. For each I, there may be defined a one set, or a plurality ofsets, each of which may pertain to a different transmission mode, e.g.coding scheme.

A set of code rates may comprise a definite or indefinite number of coderates, and/or the number may be explicitly or implicitly limited. Forexample, if the code rate is indicated with a bandwidth indication, thepossible number of code rates may be implicitly limited by the maximumbandwidth that may be indicated or allocated or scheduled. It should benoted that, generally, a set of code rates may be implicitly defined bythe code rates allowable and/or available and/or indicatable and/orconfigurable. A set of code rates, or different sets, may be predefinedand/or configured or configurable, e.g. by higher layer signaling, e.g.RRC signaling or MAC signaling. A set, or different sets, may berepresented by or in one or more tables. A code rate indication mayindicate a set out of different sets and/or a code rate out of the set,e.g. by indexing or referencing one or more tables.

A code rate may generally be indicated by, and/or be determined basedon, a number L of (en)coding bits to be determined based on Iinformation bits. The encoded bits may comprise E=L+I bits.

In some variants, the code rate indication may indicate and/or representa target block error rate for the feedback control signaling.

Generally, the feedback control signaling may be associated to, e.g.represent or be formatted for or according to, a physical uplink controlchannel or a physical sidelink control channel. Signaling associated toinformation may generally be considered to carry and/or represent theinformation. Signaling or information associated to a channel may betransmitted on the channel and/or be mapped or mappable to the channel,e.g. according to resources it is transmitted on, and/or based on achannel format. Feedback control signaling or information pertaining toother signaling may be feedback to that signaling or the informationthereof, e.g. acknowledgement signaling or measurement reporting. Suchsignaling or information may be determined based on, or in response to,receiving (or not receiving, or decoding or not decoding) the othersignaling.

It may be considered that in general the feedback control signaling mayrepresent uplink control information or sidelink control information,and/or may be associated to a corresponding channel. The feedbackcontrol signaling may pertain to received signaling, which may be in adirection of communication reverse or opposite to the direction it istransmitted in, e.g. feeding back information determined based on(pertaining to) the received signaling.

Receiving feedback control signaling based on the code rate and/or coderate indication may comprise decoding and/or demodulating receivedsignaling assuming the code rate has been used for encoding it, or thatit has been encoded according to the code rate indication. Such decodingmay in particular assume a mapping of bits to resources and/ormodulation symbols in line with the code rate or code rate indication.

Also, a program product comprising instructions causing processingcircuitry to control and/or perform a method as described herein isdisclosed.

A carrier medium arrangement carrying and/or storing a program productas described herein is also considered—

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings are provided to illustrate concepts and approachesdescribed herein, and are not intended to limit their scope. Thedrawings comprise:

FIG. 1 , schematically showing the encoding of a short PUCCH;

FIG. 2 , schematically showing the encoding of a long PUCCH;

FIG. 3 , schematically showing different arrangements of an anchor RB;

FIG. 4 , schematically showing an exemplary radio node implemented asuser equipment; and

FIG. 5 , schematically showing an exemplary radio node implemented asnetwork node.

DETAILED DESCRIPTION

In the following, approaches are illustrated with reference to NR RAN,in the context of feedback control signaling being associated to uplinkcontrol information (specifically, UCI according to NR) or associatedsignaling. UCI may comprise for example ACK/NACK, CQI/CSI, SR,beam-related parameters or any combination thereof.

NR defines a multitude of different PUCCH formats, among others a shortand long PUCCH format that can carry more than 2 bits up to a few 10bits and up to a few 100 bits, respectively. To be capable of supportingsuch large payload variations these two PUCCH formats have variablebandwidth depending on the UCI size.

FIG. 1 shows a schematic representation of short PUCCH format for morethan 2 bits (representing I). The UCI (ACK/NACK, CQI/CSI, SR,beam-related parameters and any combination thereof) is encoded, mappedto modulation symbols which are mapped to subcarriers of one OFDM symbolcarrying UCI, e.g. as scheduled for UCI/PUCCH transmission. FDMed withthe UCI-carrying subcarriers may be DM-RS to facilitate demodulation ofthe signaling. The number of allocated RBs (representing the bandwidth)is variable and may depend on the UCI size. A similar structure existsfor a two symbol long short PUCCH. In particular, FIG. 1 shows a ShortPUCCH format for more than 2 bits. The encoding may be based on a coderate indication, which may indicate which code rate to use.

FIG. 2 shows a schematic representation of long PUCCH format for morethan 2 bits. Long PUCCH comes with variable length (in time domain)ranging from 4 symbols to a complete slot and even multiple slots (orother transmission timing structures). The UCI (ACK/NACK, CQI/CSI, SR,beam-related parameters or any combination thereof) is encoded, e.g.,based on a code rate indication, and mapped to modulation symbols. Themodulation symbols are grouped into groups of modulation symbols (onegroup per OFDM symbol). DFT-precoding is applied to the symbols pergroup to obtain a low PAPR/CM. The DFT-spread modulation symbols areassigned to the allocated subcarriers and OFDM modulated. A harvestfrequency diversity frequency hopping can be applied as shown in thefigure. The number of allocated RBs is variable and depends on the UCIsize. DM-RS are mapped to separate symbols to maintain low PAPR/CM. FIG.2 in particular shows a long PUCCH format with 14 symbols for more than2 bits.

With one fixed mapping between UCI size and number of allocated RB thecode rate of the PUCCH is constant or varies only slightly, which may benot sufficient to support various use cases, among others MBB and URLLC.While the typical operating point of PUCCH for MBB is in the range ofBLER=1E-2 . . . 1E-3, the required BLER can be substantially lower forURLLC. With an almost constant code rate for PUCCH, it is difficult totarget very different BLER. The mapping between UCI size (payload size,or number I of information bits, and/or UCI bits), and bandwidth(represented by the number of allocated RBs) may be indicated by thecode rate indication, which for example may indicate one code rate froma set of possible code rates to be used.

According to approaches described herein, e.g. as part of the PUCCHresource configuration, a target code rate of the PUCCH can bespecified, e.g. utilizing the code rate indication. This may result indifferent slopes of the UCI→#RB mapping. The network has good controlover the PUCCH code rate and thus can easily adopt PUCCH reliability tothe different NR usage scenarios, such as MBB and URLLC.

For example as part of the PUCCH configuration, a target code rate ofthe PUCCH is specified. The actual code rate can vary slightly since thenumber of coded bits is only incremented in sizes of (fractional) RB,while UCI can change with granularity of 1 bit. For example, as part ofa PUCCH configuration a target code rate R_(tar) can be configured. With#UCI UCI bits, #RB allocated RBs, #SC the number of subcarriers per RB(e.g., 12), #symb UCI carrying symbols, and Q_(m) the bits permodulation symbol (preferable fixed QPSK, i.e. Q_m=2) the actual coderate is

$\begin{matrix}{{R_{act} = {\frac{\#\;{UCI}}{\#\;{{SC} \cdot \#}{{RB} \cdot \#}\;{{Symb} \cdot \left( {1 - {OH}_{DMRS}} \right) \cdot {Qm}}} \leq R_{tar}}},} & \left( {{Equation}\mspace{14mu} 1} \right)\end{matrix}$which should be smaller than the target code rate. The number ofallocated RB becomes then

$\begin{matrix}{{\#{RB}} = {\left\lceil \frac{\#{UCI}}{{R_{tar} \cdot \#}{{Symb} \cdot \left( {1 - {OH}_{DMRS}} \right) \cdot {Qm}}} \right\rceil.}} & \left( {{Equation}\mspace{14mu} 2} \right)\end{matrix}$with OH_(DMRS) indicating the DM-RS overhead averaged across theUCI-carrying symbols.

Another way to describe the same principle is to configure, as part ofthe PUCCH configuration for a nominal UCI size #UCI_(nom), the RB number#RB_(nom) needed to carry the UCI bits. If the actual UCI size #UCI islarger, additional RB need to be allocated. The total number ofallocated RB can be expressed as

$\begin{matrix}{{{\#{RB}} = {{\left\lceil \frac{\#{UCI}}{\#{UCI}_{nom}} \right\rceil \cdot \#}{PRB}_{nom}}},} & \left( {{Equation}\mspace{14mu} 3} \right)\end{matrix}$if RB_(nom)=1 above formula simplifies to #RB=┌#UCI/#UCI_(nom)┐.

The PUCCH time-frequency resources (allocated or scheduled resources)may be specified with RRC signaling or dynamic DCI signaling or acombination of both. RRC signaling may configures a set of PUCCHresources (PUCCH resource pool), wherein the DCI may select (indicate)one of the configured resources. Other alternatives such that the PUCCHresource is implicitly derived from another signal parameters are alsoconsidered.

In case of a multi-RB PUCCH, the so obtained time-frequency resource(RB) may be complemented with as many RB as needed to obtain #RB RB intotal. Often, the resources in PUCCH resource pool (and also if derivedimplicitly from another parameter) will be only 1 RB wide, even thoughother values can be envisioned as well. Assuming the PUCCH resource poolprovides 1 RB, this RB can be seen as the anchor RB of the PUCCH and#RB−1 additional RBs may be added to obtain the desired PUCCH bandwidthof #RB RB. The anchor RB can be the lowest, a defined middle, or thehighest RB in bandwidth of the PUCCH. The anchor RB is then complementedwith the remaining RBs either in a contiguous or non-contiguous fashion,e.g. according to a predefined and/or configured or configurable(bandwidth) distribution.

FIG. 3 shows different examples how a 1 RB wide anchor RB iscomplemented by 3 RB to obtain #RB=4 total RBs. In a) the anchor RB isthe lowest RB in frequency and contiguously extended to higherfrequencies; in b) the PUCCH resource is also contiguous, but the anchorRB is a defined RB in the middle; and in c) the PUCCH resource consistsof 4 non-contiguous RB with the anchor RB the lowest one.

Instead of directly configuring the code rate together with a PUCCHresource (alternatively nominal UCI and RB size) one or more tables withdifferent profiles may be considered, e.g. for low, medium, and highPUCCH reliability, wherein different profiles may map to different coderates, see for example table 1. The profiles may optionally be mapped orindexed to different bandwidth distributions. A code rate indication mayindicate or index the profile and/or bandwidth distribution, and/orconfigure the table/s.

TABLE 1 Three different PUCCH reliability profiles are specified. PUCCHreliability Contiguous RB Non-contiguous RB profile allocationallocation Low R_(tar,1) R_(tar,4) Medium R_(tar,2) R_(tar,5) HighR_(tar,3) R_(tar,6)

If for a PUCCH both contiguous and non-contiguous RB allocations arespecified, the table could have two different sets of code rates, onefor contiguous and one for non-contiguous RB allocations. The code ratesfor the non-contiguous RB allocation may be set higher than thecorresponding ones from the contiguous RB allocation, since thenon-contiguous RB allocation enjoys more frequency diversity. Forexample, for the code rates R_(tar,1)≥R_(tar,2)≥R_(tar,3) andR_(tar,4)≥R_(tar,5)≥R_(tar,6) may hold.

Different UCI encoders (representing coding schemes) depending on theUCI payload may be used. For example, Reed-Muller codes may be used forup to 11 UCI bits (information bits), while Polar codes may be used forlarger UCI sizes. The encoders have different error protectioncapabilities. Instead of a single code rate, a code rate as function ofencoder could be defined, or more generally the code rate could bedefined as function of the UCI size (since even for one encoder thecoding gain depends on the information block size).

A PUCCH resource can be used for transportation of different UCI types(ACK/NACK, CQI/CSI, SR, beam-related parameters and any combinationthereof). Depending on the UCI type or the UCI type mix (combination oftypes) that is transmitted in a PUCCH transmission (feedback controlsignaling), different code rates could be configured or indicated.ACK/NACK typically has higher performance requirements than CQI/CSI, soa lower code rate could be configured for PUCCH containing ACK/NACK thanPUCCH containing CQI/CSI.

TABLE 2 Depending on the PUCCH payload, different code rates areconfigured, representing a set of code rates UCI type Target code rateUCI type 1 R_(tar,1) UCI type 2 R_(tar,2) UCI type 3 R_(tar,3) UCI mix 1R_(tar,4) UCI mix 2 R_(tar,5)

A UCI mix could be just defined by which UCI types are mixed (e.g.ACK/NACK and CQI/CSI) or could depend both on the mixed UCI types, butalso on the sizes or fraction of sizes of the mixed UCI types.Accordingly, the set of code rates could be depended on the informationtype and/or the payload size.

A PUCCH could be transmitted in response to a downlink transmissionassociated with certain QoS requirements, such as BLER and/or priorityand/or latency. If the downlink transmission requires high reliability,high reliability for the HARQ feedback may be required as well. Thus,the reliability and code rate associated with the corresponding PUCCHtransmission can depend on QoS requirements of the downlinktransmission. When configuring the PUCCH resource, a table can beconfigured that maps DL QoS requirements to PUCCH target code rates orto PUCCH target BLER, which can then be mapped to PUCCH target coderates. The DL QoS requirements could be known to the UE based on bitfield in the DCI message that indicates a DL transmission profile. Eachtransmission profile would then map to PUCCH reliability requirements.It could be further considered that the PUCCH reliability requirementsare derived based on the properties of the PDSCH. The PDSCH propertiescould be on or a combination of code rate, modulation order, time domainallocation, frequency domain allocation, numerology, cyclic prefix, TBSsize, waveform, carrier, bandwidth part, number of layers, QCLinformation and potentially together with other properties not listedhere. These characteristics described here may be consideredtransmission mode characteristics.

A PUCCH resource for PUCCH formats that support variable bandwidth(number of RB) can be configured with a target code rate. The targetcode rate determines how fast/slow the PUCCH bandwidth grows as functionof the UCI size. If a high target code rate is specified, the requirednumber of PUCCH RB grows slower than if a low code rate is configured.Via the configured target code rate the e/gNB has control over the PUCCHreliability which is needed to support different use cases such as MBBor URLLC.

FIG. 4 schematically shows a radio node, in particular a terminal orwireless device 10, which may in particular be implemented as a UE (UserEquipment). Radio node 10 comprises processing circuitry (which may alsobe referred to as control circuitry) 20, which may comprise a controllerconnected to a memory. Any module of the radio node 10, e.g. acommunicating module or determining module, may be implemented in and/orexecutable by, the processing circuitry 20, in particular as module inthe controller. Radio node 10 also comprises radio circuitry 22providing receiving and transmitting or transceiving functionality(e.g., one or more transmitters and/or receivers and/or transceivers),the radio circuitry 22 being connected or connectable to the processingcircuitry. An antenna circuitry 24 of the radio node 10 is connected orconnectable to the radio circuitry 22 to collect or send and/or amplifysignals. Radio circuitry 22 and the processing circuitry 20 controllingit are configured for cellular communication with a network, e.g. a RANas described herein, and/or for sidelink communication. Radio node 10may generally be adapted to carry out any of the methods of operating aradio node like terminal or UE disclosed herein; in particular, it maycomprise corresponding circuitry, e.g. processing circuitry, and/ormodules.

FIG. 5 schematically show a radio node 100, which may in particular beimplemented as a network node 100, for example an eNB or gNB or similarfor NR. Radio node 100 comprises processing circuitry (which may also bereferred to as control circuitry) 120, which may comprise a controllerconnected to a memory. Any module, e.g. transmitting module and/orreceiving module and/or configuring module of the node 100 may beimplemented in and/or executable by the processing circuitry 120. Theprocessing circuitry 120 is connected to control radio circuitry 122 ofthe node 100, which provides receiver and transmitter and/or transceiverfunctionality (e.g., comprising one or more transmitters and/orreceivers and/or transceivers). An antenna circuitry 124 may beconnected or connectable to radio circuitry 122 for signal reception ortransmittance and/or amplification. Node 100 may be adapted to carry outany of the methods for operating a radio node or network node disclosedherein; in particular, it may comprise corresponding circuitry, e.g.processing circuitry, and/or modules. The antenna circuitry 124 may beconnected to and/or comprise an antenna array. The node 100,respectively its circuitry, may be adapted to perform any of the methodsof operating a network node or a radio node as described herein; inparticular, it may comprise corresponding circuitry, e.g. processingcircuitry, and/or modules. The radio node 100 may generally comprisecommunication circuitry, e.g. for communication with another networknode, like a radio node, and/or with a core network and/or an internetor local net, in particular with an information system, which mayprovide information and/or data to be transmitted to a user equipment.

References to specific resource structures like transmission timingstructure and/or symbol and/or slot and/or mini-slot and/or subcarrierand/or carrier may pertain to a specific numerology, which may bepredefined and/or configured or configurable. A transmission timingstructure may represent a time interval, which may cover one or moresymbols. Some examples of a transmission timing structure aretransmission time interval (TTI), subframe, slot and mini-slot. A slotmay comprise a predetermined, e.g. predefined and/or configured orconfigurable, number of symbols, e.g. 6 or 7, or 12 or 14. A mini-slotmay comprise a number of symbols (which may in particular beconfigurable or configured) smaller than the number of symbols of aslot, in particular 1, 2, 3 or 4 symbols. A transmission timingstructure may cover a time interval of a specific length, which may bedependent on symbol time length and/or cyclic prefix used. Atransmission timing structure may pertain to, and/or cover, a specifictime interval in a time stream, e.g. synchronized for communication.Timing structures used and/or scheduled for transmission, e.g. slotand/or mini-slots, may be scheduled in relation to, and/or synchronizedto, a timing structure provided and/or defined by other transmissiontiming structures. Such transmission timing structures may define atiming grid, e.g., with symbol time intervals within individualstructures representing the smallest timing units. Such a timing gridmay for example be defined by slots or subframes (wherein in some cases,subframes may be considered specific variants of slots). A transmissiontiming structure may have a duration (length in time) determined basedon the durations of its symbols, possibly in addition to cyclicprefix/es used. The symbols of a transmission timing structure may havethe same duration, or may in some variants have different duration. Thenumber of symbols in a transmission timing structure may be predefinedand/or configured or configurable, and/or be dependent on numerology.The timing of a mini-slot may generally be configured or configurable,in particular by the network and/or a network node. The timing may beconfigurable to start and/or end at any symbol of the transmissiontiming structure, in particular one or more slots.

There is generally considered a program product comprising instructionsadapted for causing processing and/or control circuitry to carry outand/or control any method described herein, in particular when executedon the processing and/or control circuitry. Also, there is considered acarrier medium arrangement carrying and/or storing a program product asdescribed herein.

A carrier medium arrangement may comprise one or more carrier media.Generally, a carrier medium may be accessible and/or readable and/orreceivable by processing or control circuitry. Storing data and/or aprogram product and/or code may be seen as part of carrying data and/ora program product and/or code. A carrier medium generally may comprise aguiding/transporting medium and/or a storage medium. Aguiding/transporting medium may be adapted to carry and/or carry and/orstore signals, in particular electromagnetic signals and/or electricalsignals and/or magnetic signals and/or optical signals. A carriermedium, in particular a guiding/transporting medium, may be adapted toguide such signals to carry them. A carrier medium, in particular aguiding/transporting medium, may comprise the electromagnetic field,e.g. radio waves or microwaves, and/or optically transmissive material,e.g. glass fiber, and/or cable. A storage medium may comprise at leastone of a memory, which may be volatile or non-volatile, a buffer, acache, an optical disc, magnetic memory, flash memory, etc.

In general, a numerology and/or subcarrier spacing may indicate thebandwidth (in frequency domain) of a subcarrier of a carrier, and/or thenumber of subcarriers in a carrier and/or the numbering of thesubcarriers in a carrier. Different numerologies may in particular bedifferent in the bandwidth of a subcarrier. In some variants, all thesubcarriers in a carrier have the same bandwidth associated to them. Thenumerology and/or subcarrier spacing may be different between carriersin particular regarding the subcarrier bandwidth. A symbol time length,and/or a time length of a timing structure pertaining to a carrier maybe dependent on the carrier frequency, and/or the subcarrier spacingand/or the numerology. In particular, different numerologies may havedifferent symbol time lengths.

Signaling may generally comprise one or more symbols and/or signalsand/or messages. A signal may comprise or represent one or more bits. Anindication may represent signaling, and/or be implemented as a signal,or as a plurality of signals. One or more signals may be included inand/or represented by a message. Signaling, in particular controlsignaling, may comprise a plurality of signals and/or messages, whichmay be transmitted on different carriers and/or be associated todifferent signaling processes, e.g. representing and/or pertaining toone or more such processes and/or corresponding information. Anindication may comprise signaling, and/or a plurality of signals and/ormessages and/or may be comprised therein, which may be transmitted ondifferent carriers and/or be associated to different acknowledgementsignaling processes, e.g. representing and/or pertaining to one or moresuch processes. Signaling associated to a channel may be transmittedsuch that represents signaling and/or information for that channel,and/or that the signaling is interpreted by the transmitter and/orreceiver to belong to that channel. Such signaling may generally complywith transmission parameters and/or format/s for the channel.

Reference signaling may be signaling comprising one or more referencesymbols and/or structures. Reference signaling may be adapted forgauging and/or estimating and/or representing transmission conditions,e.g. channel conditions and/or transmission path conditions and/orchannel (or signal or transmission) quality. It may be considered thatthe transmission characteristics (e.g., signal strength and/or formand/or modulation and/or timing) of reference signaling are availablefor both transmitter and receiver of the signaling (e.g., due to beingpredefined and/or configured or configurable and/or being communicated).Different types of reference signaling may be considered, e.g.pertaining to uplink, downlink or sidelink, cell-specific (inparticular, cell-wide, e.g., CRS) or device or user specific (addressedto a specific target or user equipment, e.g., CSI-RS),demodulation-related (e.g., DMRS) and/or signal strength related, e.g.power-related or energy-related or amplitude-related (e.g., SRS or pilotsignaling) and/or phase-related, etc.

Uplink or sidelink signaling may be OFDMA (Orthogonal Frequency DivisionMultiple Access) or SC-FDMA (Single Carrier Frequency Division MultipleAccess) signaling. Downlink signaling may in particular be OFDMAsignaling. However, signaling is not limited thereto (Filter-Bank basedsignaling may be considered one alternative).

A radio node may generally be considered a device or node adapted forwireless and/or radio (and/or microwave) frequency communication, and/orfor communication utilizing an air interface, e.g. according to acommunication standard.

A radio node may be a network node, or a user equipment or terminal. Anetwork node may be any radio node of a wireless communication network,e.g. a base station and/or gNodeB (gNB) and/or eNodeB (eNB) and/or relaynode and/or micro/nano/pico/femto node and/or other node, in particularfor a RAN as described herein.

The terms wireless device, user equipment (UE) and terminal may beconsidered to be interchangeable in the context of this disclosure. Awireless device, user equipment or terminal may represent an end devicefor communication utilizing the wireless communication network, and/orbe implemented as a user equipment according to a standard. Examples ofuser equipments may comprise a phone like a smartphone, a personalcommunication device, a mobile phone or terminal, a computer, inparticular laptop, a sensor or machine with radio capability (and/oradapted for the air interface), in particular for MTC(Machine-Type-Communication, sometimes also referred to M2M,Machine-To-Machine), or a vehicle adapted for wireless communication. Auser equipment or terminal may be mobile or stationary.

A radio node may generally comprise processing circuitry and/or radiocircuitry. A radio node, in particular a network node, may in some casescomprise cable circuitry and/or communication circuitry, with which itmay be connected or connectable to another radio node and/or a corenetwork.

Circuitry may comprise integrated circuitry. Processing circuitry maycomprise one or more processors and/or controllers (e.g.,microcontrollers), and/or ASICs (Application Specific IntegratedCircuitry) and/or FPGAs (Field Programmable Gate Array), or similar. Itmay be considered that processing circuitry comprises, and/or is(operatively) connected or connectable to one or more memories or memoryarrangements. A memory arrangement may comprise one or more memories. Amemory may be adapted to store digital information. Examples formemories comprise volatile and non-volatile memory, and/or Random AccessMemory (RAM), and/or Read-Only-Memory (ROM), and/or magnetic and/oroptical memory, and/or flash memory, and/or hard disk memory, and/orEPROM or EEPROM (Erasable Programmable ROM or Electrically ErasableProgrammable ROM).

Radio circuitry may comprise one or more transmitters and/or receiversand/or transceivers (a transceiver may operate or be operable astransmitter and receiver, and/or may comprise joint or separatedcircuitry for receiving and transmitting, e.g. in one package orhousing), and/or may comprise one or more amplifiers and/or oscillatorsand/or filters, and/or may comprise, and/or be connected or connectableto antenna circuitry and/or one or more antennas and/or antenna arrays.An antenna array may comprise one or more antennas, which may bearranged in a dimensional array, e.g. 2D or 3D array, and/or antennapanels. A remote radio head (RRH) may be considered as an example of anantenna array. However, in some variants, a RRH may be also beimplemented as a network node, depending on the kind of circuitry and/orfunctionality implemented therein.

Communication circuitry may comprise radio circuitry and/or cablecircuitry. Communication circuitry generally may comprise one or moreinterfaces, which may be air interface/s and/or cable interface/s and/oroptical interface/s, e.g. laser-based. Interface/s may be in particularpacket-based. Cable circuitry and/or a cable interfaces may comprise,and/or be connected or connectable to, one or more cables (e.g., opticalfiber-based and/or wire-based), which may be directly or indirectly(e.g., via one or more intermediate systems and/or interfaces) beconnected or connectable to a target, e.g. controlled by communicationcircuitry and/or processing circuitry.

Any one or all of the modules disclosed herein may be implemented insoftware and/or firmware and/or hardware. Different modules may beassociated to different components of a radio node, e.g. differentcircuitries or different parts of a circuitry. It may be considered thata module is distributed over different components and/or circuitries. Aprogram product as described herein may comprise the modules related toa device on which the program product is intended (e.g., a userequipment or network node) to be executed (the execution may beperformed on, and/or controlled by the associated circuitry).

A radio access network may be a wireless communication network, and/or aRadio Access Network (RAN) in particular according to a communicationstandard. A communication standard may in particular a standardaccording to 3GPP and/or 5G, e.g. according to NR or LTE, in particularLTE Evolution.

A wireless communication network may be and/or comprise a Radio AccessNetwork (RAN), which may be and/or comprise any kind of cellular and/orwireless radio network, which may be connected or connectable to a corenetwork. The approaches described herein are particularly suitable for a5G network, e.g. LTE Evolution and/or NR (New Radio), respectivelysuccessors thereof. A RAN may comprise one or more network nodes, and/orone or more terminals, and/or one or more radio nodes. A network nodemay in particular be a radio node adapted for radio and/or wirelessand/or cellular communication with one or more terminals. A terminal maybe any device adapted for radio and/or wireless and/or cellularcommunication with or within a RAN, e.g. a user equipment (UE) or mobilephone or smartphone or computing device or vehicular communicationdevice or device for machine-type-communication (MTC), etc. A terminalmay be mobile, or in some cases stationary. A RAN or a wirelesscommunication network may comprise at least one network node and a UE,or at least two radio nodes. There may be generally considered awireless communication network or system, e.g. a RAN or RAN system,comprising at least one radio node, and/or at least one network node andat least one terminal.

Transmitting in downlink may pertain to transmission from the network ornetwork node to the terminal. Transmitting in uplink may pertain totransmission from the terminal to the network or network node.Transmitting in sidelink may pertain to (direct) transmission from oneterminal to another. Uplink, downlink and sidelink (e.g., sidelinktransmission and reception) may be considered communication directions.In some variants, uplink and downlink may also be used to describedwireless communication between network nodes, e.g. for wireless backhauland/or relay communication and/or (wireless) network communication forexample between base stations or similar network nodes, in particularcommunication terminating at such. It may be considered that backhauland/or relay communication and/or network communication is implementedas a form of sidelink or uplink communication or similar thereto.

Control information or a control information message or correspondingsignaling (control signaling) may be transmitted on a control channel,e.g. a physical control channel, which may be a downlink channel or (ora sidelink channel in some cases, e.g. one UE scheduling another UE).For example, control information/allocation information may be signaledby a network node on PDCCH (Physical Downlink Control Channel) and/or aPDSCH (Physical Downlink Shared Channel) and/or a HARQ-specific channel.Acknowledgement signaling, e.g. as a form of uplink control informationor signaling, may be transmitted by a terminal on a PUCCH (PhysicalUplink Control Channel) and/or PUSCH (Physical Uplink Shared Channel)and/or a HARQ-specific channel. Multiple channels may apply formulti-component/multi-carrier indication or signaling.

Signaling may generally be considered to represent an electromagneticwave structure (e.g., over a time interval and frequency interval),which is intended to convey information to at least one specific orgeneric (e.g., anyone who might pick up the signaling) target. A processof signaling may comprise transmitting the signaling. Transmittingsignaling, in particular control signaling or communication signaling,e.g. comprising or representing acknowledgement signaling and/orresource requesting information, may comprise encoding and/ormodulating. Encoding and/or modulating may comprise error detectioncoding and/or forward error correction encoding and/or scrambling.Receiving control signaling may comprise corresponding decoding and/ordemodulation. Error detection coding may comprise, and/or be based on,parity or checksum approaches, e.g. CRC (Cyclic Redundancy Check).Forward error correction coding may comprise and/or be based on forexample turbo coding and/or Reed-Muller coding, and/or polar codingand/or LDPC coding (Low Density Parity Check). The type of coding usedmay be based on the channel (e.g., physical channel) the coded signal isassociated to. A code rate may represent the ratio of the number ofinformation bits before encoding to the number of encoded bits afterencoding, considering that encoding adds coding bits for error detectioncoding and forward error correction.

Communication signaling may comprise, and/or represent, and/or beimplemented as, data signaling, and/or user plane signaling.Communication signaling may be associated to a data channel, e.g. aphysical downlink channel or physical uplink channel or physicalsidelink channel, in particular a PDSCH (Physical Downlink SharedChannel) or PSSCH (Physical Sidelink Shared Channel). Generally, a datachannel may be a shared channel or a dedicated channel. Data signalingmay be signaling associated to and/or on a data channel.

An indication generally may explicitly and/or implicitly indicate theinformation it represents and/or indicates. Implicit indication may forexample be based on position and/or resource used for transmission.Explicit indication may for example be based on a parametrization withone or more parameters, and/or one or more index or indices, and/or oneor more bit patterns representing the information. It may in particularbe considered that control signaling as described herein, based on theutilized resource sequence, implicitly indicates the control signalingtype.

A resource element may generally describe the smallest individuallyusable and/or encodable and/or decodable and/or modulatable and/ordemodulatable time-frequency resource, and/or may describe atime-frequency resource covering a symbol time length in time and asubcarrier in frequency. A signal may be allocatable and/or allocated toa resource element. A subcarrier may be a subband of a carrier, e.g. asdefined by a standard. A carrier may define a frequency and/or frequencyband for transmission and/or reception. In some variants, a signal(jointly encoded/modulated) may cover more than one resource elements. Aresource element may generally be as defined by a correspondingstandard, e.g. NR or LTE. As symbol time length and/or subcarrierspacing (and/or numerology) may be different between different symbolsand/or subcarriers, different resource elements may have differentextension (length/width) in time and/or frequency domain, in particularresource elements pertaining to different carriers.

A resource generally may represent a time-frequency and/or coderesource, on which signaling, e.g. according to a specific format, maybe communicated, for example transmitted and/or received, and/or beintended for transmission and/or reception.

A border symbol may generally represent a starting symbol or an endingsymbol for transmitting and/or receiving. A starting symbol may inparticular be a starting symbol of uplink or sidelink signaling, forexample control signaling or data signaling. Such signaling may be on adata channel or control channel, e.g. a physical channel, in particulara physical uplink shared channel (like PUSCH) or a sidelink data orshared channel, or a physical uplink control channel (like PUCCH) or asidelink control channel. If the starting symbol is associated tocontrol signaling (e.g., on a control channel), the control signalingmay be in response to received signaling (in sidelink or downlink), e.g.representing acknowledgement signaling associated thereto, which may beHARQ or ARQ signaling. An ending symbol may represent an ending symbol(in time) of downlink or sidelink transmission or signaling, which maybe intended or scheduled for the radio node or user equipment. Suchdownlink signaling may in particular be data signaling, e.g. on aphysical downlink channel like a shared channel, e.g. a PDSCH (PhysicalDownlink Shared Channel). A starting symbol may be determined based on,and/or in relation to, such an ending symbol.

Configuring a radio node, in particular a terminal or user equipment,may refer to the radio node being adapted or caused or set and/orinstructed to operate according to the configuration. Configuring may bedone by another device, e.g., a network node (for example, a radio nodeof the network like a base station or eNodeB) or network, in which caseit may comprise transmitting configuration data to the radio node to beconfigured. Such configuration data may represent the configuration tobe configured and/or comprise one or more instruction pertaining to aconfiguration, e.g. a configuration for transmitting and/or receiving onallocated resources, in particular frequency resources. A radio node mayconfigure itself, e.g., based on configuration data received from anetwork or network node. A network node may utilize, and/or be adaptedto utilize, its circuitry/ies for configuring. Allocation informationmay be considered a form of configuration data. Configuration data maycomprise and/or be represented by configuration information, and/or oneor more corresponding indications and/or message/s

Generally, configuring may include determining configuration datarepresenting the configuration and providing, e.g. transmitting, it toone or more other nodes (parallel and/or sequentially), which maytransmit it further to the radio node (or another node, which may berepeated until it reaches the wireless device). Alternatively, oradditionally, configuring a radio node, e.g., by a network node or otherdevice, may include receiving configuration data and/or data pertainingto configuration data, e.g., from another node like a network node,which may be a higher-level node of the network, and/or transmittingreceived configuration data to the radio node. Accordingly, determininga configuration and transmitting the configuration data to the radionode may be performed by different network nodes or entities, which maybe able to communicate via a suitable interface, e.g., an X2 interfacein the case of LTE or a corresponding interface for NR. Configuring aterminal may comprise scheduling downlink and/or uplink transmissionsfor the terminal, e.g. downlink data and/or downlink control signalingand/or DCI and/or uplink control or data or communication signaling, inparticular acknowledgement signaling, and/or configuring resourcesand/or a resource pool therefor.

A resource structure may be considered to be neighbored in frequencydomain by another resource structure, if they share a common borderfrequency, e.g. one as an upper frequency border and the other as alower frequency border. Such a border may for example be represented bythe upper end of a bandwidth assigned to a subcarrier n, which alsorepresents the lower end of a bandwidth assigned to a subcarrier n+1. Aresource structure may be considered to be neighbored in time domain byanother resource structure, if they share a common border time, e.g. oneas an upper (or right in the figures) border and the other as a lower(or left in the figures) border. Such a border may for example berepresented by the end of the symbol time interval assigned to a symboln, which also represents the beginning of a symbol time intervalassigned to a symbol n+1.

Generally, a resource structure being neighbored by another resourcestructure in a domain may also be referred to as abutting and/orbordering the other resource structure in the domain.

A resource structure may general represent a structure in time and/orfrequency domain, in particular representing a time interval and afrequency interval. A resource structure may comprise and/or becomprised of resource elements, and/or the time interval of a resourcestructure may comprise and/or be comprised of symbol time interval/s,and/or the frequency interval of a resource structure may compriseand/or be comprised of subcarrier/s. A resource element may beconsidered an example for a resource structure, a slot or mini-slot or aPhysical Resource Block (PRB) or parts thereof may be considered others.A resource structure may be associated to a specific channel, e.g. aPUSCH or PUCCH, in particular resource structure smaller than a slot orPRB.

A carrier may generally represent a frequency range or band and/orpertain to a central frequency and an associated frequency interval. Itmay be considered that a carrier comprises a plurality of subcarriers. Acarrier may have assigned to it a central frequency or center frequencyinterval, e.g. represented by one or more subcarriers (to eachsubcarrier there may be generally assigned a frequency bandwidth orinterval). Different carriers may be non-overlapping, and/or may beneighboring in frequency domain.

It should be noted that the term “radio” in this disclosure may beconsidered to pertain to wireless communication in general, and may alsoinclude wireless communication utilizing microwave and/or millimeterand/or other frequencies, in particular between 100 MHz or 1 GHz, and100 GHz or 20 or 10 GHz. Such communication may utilize one or morecarriers.

A radio node, in particular a network node or a terminal, may generallybe any device adapted for transmitting and/or receiving radio and/orwireless signals and/or data, in particular communication data, inparticular on at least one carrier. The at least one carrier maycomprise a carrier accessed based on a LBT procedure (which may becalled LBT carrier), e.g., an unlicensed carrier. It may be consideredthat the carrier is part of a carrier aggregate.

Receiving or transmitting on a cell or carrier may refer to receiving ortransmitting utilizing a frequency (band) or spectrum associated to thecell or carrier. A cell may generally comprise and/or be defined by orfor one or more carriers, in particular at least one carrier for ULcommunication/transmission (called UL carrier) and at least one carrierfor DL communication/transmission (called DL carrier). It may beconsidered that a cell comprises different numbers of UL carriers and DLcarriers. Alternatively, or additionally, a cell may comprise at leastone carrier for UL communication/transmission and DLcommunication/transmission, e.g., in TDD-based approaches.

A channel may generally be a logical, transport or physical channel. Achannel may comprise and/or be arranged on one or more carriers, inparticular a plurality of subcarriers. A channel carrying and/or forcarrying control signaling/control information may be considered acontrol channel, in particular if it is a physical layer channel and/orif it carries control plane information. Analogously, a channel carryingand/or for carrying data signaling/user information may be considered adata channel, in particular if it is a physical layer channel and/or ifit carries user plane information. A channel may be defined for aspecific communication direction, or for two complementary communicationdirections (e.g., UL and DL, or sidelink in two directions), in whichcase it may be considered to have two component channels, one for eachdirection. Examples of channels comprise a channel for low latencyand/or high reliability transmission, in particular a channel forUltra-Reliable Low Latency Communication (URLLC), which may be forcontrol and/or data.

In general, a symbol may represent and/or be associated to a symbol timelength, which may be dependent on the carrier and/or subcarrier spacingand/or numerology of the associated carrier. Accordingly, a symbol maybe considered to indicate a time interval having a symbol time length inrelation to frequency domain. A symbol time length may be dependent on acarrier frequency and/or bandwidth and/or numerology and/or subcarrierspacing of, or associated to, a symbol. Accordingly, different symbolsmay have different symbol time lengths. In particular, numerologies withdifferent subcarrier spacings may have different symbol time length.Generally, a symbol time length may be based on, and/or include, a guardtime interval or cyclic extension, e.g. prefix or postfix.

A sidelink may generally represent a communication channel (or channelstructure) between two UEs and/or terminals, in which data istransmitted between the participants (UEs and/or terminals) via thecommunication channel, e.g. directly and/or without being relayed via anetwork node. A sidelink may be established only and/or directly via airinterface/s of the participant, which may be directly linked via thesidelink communication channel. In some variants, sidelink communicationmay be performed without interaction by a network node, e.g. on fixedlydefined resources and/or on resources negotiated between theparticipants. Alternatively, or additionally, it may be considered thata network node provides some control functionality, e.g. by configuringresources, in particular one or more resource pool/s, for sidelinkcommunication, and/or monitoring a sidelink, e.g. for charging purposes.

Sidelink communication may also be referred to as device-to-device (D2D)communication, and/or in some cases as ProSe (Proximity Services)communication, e.g. in the context of LTE. A sidelink may be implementedin the context of V2x communication (Vehicular communication), e.g. V2V(Vehicle-to-Vehicle), V2I (Vehicle-to-Infrastructure) and/or V2P(Vehicle-to-Person). Any device adapted for sidelink communication maybe considered a user equipment or terminal.

A sidelink communication channel (or structure) may comprise one or more(e.g., physical or logical) channels, e.g. a PSCCH (Physical SidelinkControl CHannel, which may for example carry control information like anacknowledgement position indication, and/or a PSSCH (Physical SidelinkShared CHannel, which for example may carry data and/or acknowledgementsignaling). It may be considered that a sidelink communication channel(or structure) pertains to and/or used one or more carrier/s and/orfrequency range/s associated to, and/or being used by, cellularcommunication, e.g. according to a specific license and/or standard.Participants may share a (physical) channel and/or resources, inparticular in frequency domain and/or related to a frequency resourcelike a carrier) of a sidelink, such that two or more participantstransmit thereon, e.g. simultaneously, and/or time-shifted, and/or theremay be associated specific channels and/or resources to specificparticipants, so that for example only one participant transmits on aspecific channel or on a specific resource or specific resources, e.g.,in frequency domain and/or related to one or more carriers orsubcarriers.

A sidelink may comply with, and/or be implemented according to, aspecific standard, e.g. a LTE-based standard and/or NR. A sidelink mayutilize TDD (Time Division Duplex) and/or FDD (Frequency DivisionDuplex) technology, e.g. as configured by a network node, and/orpreconfigured and/or negotiated between the participants. A userequipment may be considered to be adapted for sidelink communication ifit, and/or its radio circuitry and/or processing circuitry, is adaptedfor utilizing a sidelink, e.g. on one or more frequency ranges and/orcarriers and/or in one or more formats, in particular according to aspecific standard. It may be generally considered that a Radio AccessNetwork is defined by two participants of a sidelink communication.Alternatively, or additionally, a Radio Access Network may berepresented, and/or defined with, and/or be related to a network nodeand/or communication with such a node.

Communication or communicating may generally comprise transmittingand/or receiving signaling. Communication on a sidelink (or sidelinksignaling) may comprise utilizing the sidelink for communication(respectively, for signaling). Sidelink transmission and/or transmittingon a sidelink may be considered to comprise transmission utilizing thesidelink, e.g. associated resources and/or transmission formats and/orcircuitry and/or the air interface. Sidelink reception and/or receivingon a sidelink may be considered to comprise reception utilizing thesidelink, e.g. associated resources and/or transmission formats and/orcircuitry and/or the air interface. Sidelink control information (e.g.,SCI) may generally be considered to comprise control informationtransmitted utilizing a sidelink.

Generally, carrier aggregation (CA) may refer to the concept of a radioconnection and/or communication link between a wireless and/or cellularcommunication network and/or network node and a terminal or on asidelink comprising a plurality of carriers for at least one directionof transmission (e.g. DL and/or UL), as well as to the aggregate ofcarriers. A corresponding communication link may be referred to ascarrier aggregated communication link or CA communication link; carriersin a carrier aggregate may be referred to as component carriers (CC). Insuch a link, data may be transmitted over more than one of the carriersand/or all the carriers of the carrier aggregation (the aggregate ofcarriers). A carrier aggregation may comprise one (or more) dedicatedcontrol carriers and/or primary carriers (which may e.g. be referred toas primary component carrier or PCC), over which control information maybe transmitted, wherein the control information may refer to the primarycarrier and other carriers, which may be referred to as secondarycarriers (or secondary component carrier, SCC). However, in someapproaches, control information may be sent over more than one carrierof an aggregate, e.g. one or more PCCs and one PCC and one or more SCCs.

A transmission may generally pertain to a specific channel and/orspecific resources, in particular with a starting symbol and endingsymbol in time, covering the interval therebetween. A scheduledtransmission may be a transmission scheduled and/or expected and/or forwhich resources are scheduled or provided or reserved. However, notevery scheduled transmission has to be realized. For example, ascheduled downlink transmission may not be received, or a scheduleduplink transmission may not be transmitted due to power limitations, orother influences (e.g., a channel on an unlicensed carrier beingoccupied). A transmission may be scheduled for a transmission timingsubstructure (e.g., a mini-slot, and/or covering only a part of atransmission timing structure) within a transmission timing structurelike a slot. A border symbol may be indicative of a symbol in thetransmission timing structure at which the transmission starts or ends.

Predefined in the context of this disclosure may refer to the relatedinformation being defined for example in a standard, and/or beingavailable without specific configuration from a network or network node,e.g. stored in memory, for example independent of being configured.Configured or configurable may be considered to pertain to thecorresponding information being set/configured, e.g. by the network or anetwork node.

A configuration or schedule, like a mini-slot configuration and/orstructure configuration, may schedule transmissions, e.g. for thetime/transmissions it is valid, and/or transmissions may be scheduled byseparate signaling or separate configuration, e.g. separate RRCsignaling and/or downlink control information signaling. Thetransmission/s scheduled may represent signaling to be transmitted bythe device for which it is scheduled, or signaling to be received by thedevice for which it is scheduled, depending on which side of acommunication the device is. It should be noted that downlink controlinformation or specifically DCI signaling may be considered physicallayer signaling, in contrast to higher layer signaling like MAC (MediumAccess Control) signaling or RRC layer signaling. The higher the layerof signaling is, the less frequent/the more time/resource consuming itmay be considered, at least partially due to the information containedin such signaling having to be passed on through several layers, eachlayer requiring processing and handling.

A scheduled transmission, and/or transmission timing structure like amini-slot or slot, may pertain to a specific channel, in particular aphysical uplink shared channel, a physical uplink control channel, or aphysical downlink shared channel, e.g. PUSCH, PUCCH or PDSCH, and/or maypertain to a specific cell and/or carrier aggregation. A correspondingconfiguration, e.g. scheduling configuration or symbol configuration maypertain to such channel, cell and/or carrier aggregation. It may beconsidered that the scheduled transmission represents transmission on aphysical channel, in particular a shared physical channel, for example aphysical uplink shared channel or physical downlink shared channel. Forsuch channels, semi-persistent configuring may be particularly suitable.

Generally, a configuration may be a configuration indicating timing,and/or be represented or configured with corresponding configurationdata. A configuration may be embedded in, and/or comprised in, a messageor configuration or corresponding data, which may indicate and/orschedule resources, in particular semi-persistently and/orsemi-statically.

A control region of a transmission timing structure may be an intervalin time for intended or scheduled or reserved for control signaling, inparticular downlink control signaling, and/or for a specific controlchannel, e.g. a physical downlink control channel like PDCCH. Theinterval may comprise, and/or consist of, a number of symbols in time,which may be configured or configurable, e.g. by (UE-specific) dedicatedsignaling (which may be single-cast, for example addressed to orintended for a specific UE), e.g. on a PDCCH, or RRC signaling, or on amulticast or broadcast channel. In general, the transmission timingstructure may comprise a control region covering a configurable numberof symbols. It may be considered that in general the border symbol isconfigured to be after the control region in time.

The duration of a symbol (symbol time length or interval) of thetransmission timing structure may generally be dependent on a numerologyand/or carrier, wherein the numerology and/or carrier may beconfigurable. The numerology may be the numerology to be used for thescheduled transmission.

Scheduling a device, or for a device, and/or related transmission orsignaling, may be considered comprising, or being a form of, configuringthe device with resources, and/or of indicating to the device resources,e.g. to use for communicating. Scheduling may in particular pertain to atransmission timing structure, or a substructure thereof (e.g., a slotor a mini-slot, which may be considered a substructure of a slot). Itmay be considered that a border symbol may be identified and/ordetermined in relation to the transmission timing structure even if fora substructure being scheduled, e.g. if an underlying timing grid isdefined based on the transmission timing structure. Signaling indicatingscheduling may comprise corresponding scheduling information and/or beconsidered to represent or contain configuration data indicating thescheduled transmission and/or comprising scheduling information. Suchconfiguration data or signaling may be considered a resourceconfiguration or scheduling configuration. It should be noted that sucha configuration (in particular as single message) in some cases may notbe complete without other configuration data, e.g. configured with othersignaling, e.g. higher layer signaling. In particular, the symbolconfiguration may be provided in addition to scheduling/resourceconfiguration to identify exactly which symbols are assigned to ascheduled transmission. A scheduling (or resource) configuration mayindicate transmission timing structure/s and/or resource amount (e.g.,in number of symbols or length in time) for a scheduled transmission.

A scheduled transmission may be transmission scheduled, e.g. by thenetwork or network node. Transmission may in this context may be uplink(UL) or downlink (DL) or sidelink (SL) transmission. A device, e.g. auser equipment, for which the scheduled transmission is scheduled, mayaccordingly be scheduled to receive (e.g., in DL or SL), or to transmit(e.g. in UL or SL) the scheduled transmission. Scheduling transmissionmay in particular be considered to comprise configuring a scheduleddevice with resource/s for this transmission, and/or informing thedevice that the transmission is intended and/or scheduled for someresources. A transmission may be scheduled to cover a time interval, inparticular a successive number of symbols, which may form a continuousinterval in time between (and including) a starting symbol and an endingsymbol. The starting symbol and the ending symbol of a (e.g., scheduled)transmission may be within the same transmission timing structure, e.g.the same slot. However, in some cases, the ending symbol may be in alater transmission timing structure than the starting symbol, inparticular a structure following in time. To a scheduled transmission, aduration may be associated and/or indicated, e.g. in a number of symbolsor associated time intervals. In some variants, there may be differenttransmissions scheduled in the same transmission timing structure. Ascheduled transmission may be considered to be associated to a specificchannel, e.g. a shared channel like PUSCH or PDSCH.

In the context of this disclosure, there may be distinguished betweendynamically scheduled or aperiodic transmission and/or configuration,and semi-static or semi-persistent or periodic transmission and/orconfiguration. The term “dynamic” or similar terms may generally pertainto configuration/transmission valid and/or scheduled and/or configuredfor (relatively) short timescales and/or a (e.g., predefined and/orconfigured and/or limited and/or definite) number of occurrences and/ortransmission timing structures, e.g. one or more transmission timingstructures like slots or slot aggregations, and/or for one or more(e.g., specific number) of transmission/occurrences. Dynamicconfiguration may be based on low-level signaling, e.g. controlsignaling on the physical layer and/or MAC layer, in particular in theform of DCI or SCI. Periodic/semi-static may pertain to longertimescales, e.g. several slots and/or more than one frame, and/or anon-defined number of occurrences, e.g., until a dynamic configurationcontradicts, or until a new periodic configuration arrives.

A transmission timing structure may comprise a plurality of symbols,and/or define an interval comprising several symbols (respectively theirassociated time intervals). In the context of this disclosure, it shouldbe noted that a reference to a symbol for ease of reference may beinterpreted to refer to the time domain projection or time interval ortime component or duration or length in time of the symbol, unless it isclear from the context that the frequency domain component also has tobe considered. Examples of transmission timing structures include slot,subframe, mini-slot (which also may be considered a substructure of aslot), slot aggregation (which may comprise a plurality of slots and maybe considered a superstructure of a slot), respectively their timedomain component. A transmission timing structure may generally comprisea plurality of symbols defining the time domain extension (e.g.,interval or length or duration) of the transmission timing structure,and arranged neighboring to each other in a numbered sequence. A timingstructure (which may also be considered or implemented assynchronization structure) may be defined by a succession of suchtransmission timing structures, which may for example define a timinggrid with symbols representing the smallest grid structures. Atransmission timing structure, and/or a border symbol or a scheduledtransmission may be determined or scheduled in relation to such a timinggrid. A transmission timing structure of reception may be thetransmission timing structure in which the scheduling control signalingis received, e.g. in relation to the timing grid. A transmission timingstructure may in particular be a slot or subframe or in some cases, amini-slot.

Feedback signaling may be considered a form or control signaling, e.g.uplink or sidelink control signaling, like UCI (Uplink ControlInformation) signaling or SCI (Sidelink Control Information) signaling.Feedback signaling may in particular comprise and/or representacknowledgement signaling and/or acknowledgement information and/ormeasurement reporting.

Acknowledgement information may comprise an indication of a specificvalue or state for an acknowledgement signaling process, e.g. ACK orNACK or DTX. Such an indication may for example represent a bit or bitvalue or bit pattern or an information switch. Different levels ofacknowledgement information, e.g. providing differentiated informationabout quality of reception and/or error position in received dataelement/s may be considered and/or represented by control signaling.Acknowledgment information may generally indicate acknowledgment ornon-acknowledgment or non-reception or different levels thereof, e.g.representing ACK or NACK or DTX. Acknowledgment information may pertainto one acknowledgement signaling process. Acknowledgement signaling maycomprise acknowledgement information pertaining to one or moreacknowledgement signaling processes, in particular one or more HARQ orARQ processes. It may be considered that to each acknowledgmentsignaling process the acknowledgement information pertains to, aspecific number of bits of the information size of the control signalingis assigned. Measurement reporting signaling may comprise measurementinformation.

Signaling may generally comprise one or more symbols and/or signalsand/or messages. A signal may comprise and/or represent one or morebits, which may be modulated into a common modulated signal. Anindication may represent signaling, and/or be implemented as a signal,or as a plurality of signals. One or more signals may be included inand/or represented by a message. Signaling, in particular controlsignaling, may comprise a plurality of signals and/or messages, whichmay be transmitted on different carriers and/or be associated todifferent acknowledgement signaling processes, e.g. representing and/orpertaining to one or more such processes. An indication may comprisesignaling and/or a plurality of signals and/or messages and/or may becomprised therein, which may be transmitted on different carriers and/orbe associated to different acknowledgement signaling processes, e.g.representing and/or pertaining to one or more such processes.

Signaling utilizing, and/or on and/or associated to, resources or aresource structure may be signaling covering the resources or structure,signaling on the associated frequency/ies and/or in the associated timeinterval/s. It may be considered that a signaling resource structurecomprises and/or encompasses one or more substructures, which may beassociated to one or more different channels and/or types of signalingand/or comprise one or more holes (resource element/s not scheduled fortransmissions or reception of transmissions). A resource substructure,e.g. a feedback resource structure, may generally be continuous in timeand/or frequency, within the associated intervals. It may be consideredthat a substructure, in particular a feedback resource structure,represents a rectangle filled with one or more resource elements intime/frequency space. However, in some cases, a resource structure orsubstructure, in particular a frequency resource range, may represent anon-continuous pattern of resources in one or more domains, e.g. timeand/or frequency. The resource elements of a substructure may bescheduled for associated signaling.

It should generally be noted that the number of bits or a bit rateassociated to specific signaling that can be carried on a resourceelement may be based on a modulation and coding scheme (MCS). Thus, bitsor a bit rate may be seen as a form of resources representing a resourcestructure or range in frequency and/or time, e.g. depending on MCS. TheMCS may be configured or configurable, e.g. by control signaling, e.g.DCI or MAC (Medium Access Control) or RRC (Radio Resource Control)signaling.

Different formats of for control information may be considered, e.g.different formats for a control channel like a Physical Uplink ControlChannel (PUCCH). PUCCH may carry control information or correspondingcontrol signaling, e.g. Uplink Control Information (UCI). UCI maycomprise feedback signaling, and/or acknowledgement signaling like HARQfeedback (ACK/NACK), and/or measurement information signaling, e.g.comprising Channel Quality Information (CQI), and/or Scheduling Request(SR) signaling. One of the supported PUCCH formats may be short, and maye.g. occur at the end of a slot interval, and/or multiplexed and/orneighboring to PUSCH. Similar control information may be provided on asidelink, e.g. as Sidelink Control Information (SCI), in particular on a(physical) sidelink control channel, like a (P)SCCH.

A code block may be considered a subelement of a data element like atransport block, e.g., a transport block may comprise a one or aplurality of code blocks.

A scheduling assignment may be configured with control signaling, e.g.downlink control signaling or sidelink control signaling. Such controlssignaling may be considered to represent and/or comprise schedulingsignaling, which may indicate scheduling information. A schedulingassignment may be considered scheduling information indicatingscheduling of signaling/transmission of signaling, in particularpertaining to signaling received or to be received by the deviceconfigured with the scheduling assignment. It may be considered that ascheduling assignment may indicate data (e.g., data block or elementand/or channel and/or data stream) and/or an (associated)acknowledgement signaling process and/or resource/s on which the data(or, in some cases, reference signaling) is to be received and/orindicate resource/s for associated feedback signaling, and/or a feedbackresource range on which associated feedback signaling is to betransmitted. Transmission associated to an acknowledgement signalingprocess, and/or the associated resources or resource structure, may beconfigured and/or scheduled, for example by a scheduling assignment.Different scheduling assignments may be associated to differentacknowledgement signaling processes. A scheduling assignment may beconsidered an example of downlink control information or signaling, e.g.if transmitted by a network node and/or provided on downlink (orsidelink control information if transmitted using a sidelink and/or by auser equipment).

A scheduling grant (e.g., uplink grant) may represent control signaling(e.g., downlink control information/signaling). It may be consideredthat a scheduling grant configures the signaling resource range and/orresources for uplink (or sidelink) signaling, in particular uplinkcontrol signaling and/or feedback signaling, e.g. acknowledgementsignaling. Configuring the signaling resource range and/or resources maycomprise configuring or scheduling it for transmission by the configuredradio node. A scheduling grant may indicate a channel and/or possiblechannels to be used/usable for the feedback signaling, in particularwhether a shared channel like a PUSCH may be used/is to be used. Ascheduling grant may generally indicate uplink resource/s and/or anuplink channel and/or a format for control information pertaining toassociated scheduling assignments. Both grant and assignment/s may beconsidered (downlink or sidelink) control information, and/or beassociated to, and/or transmitted with, different messages.

A resource structure in frequency domain (which may be referred to asfrequency interval and/or range) may be represented by a subcarriergrouping. A subcarrier grouping may comprise one or more subcarriers,each of which may represent a specific frequency interval, and/orbandwidth. The bandwidth of a subcarrier, the length of the interval infrequency domain, may be determined by the subcarrier spacing and/ornumerology. The subcarriers may be arranged such that each subcarrierneighbors at least one other subcarrier of the grouping in frequencyspace (for grouping sizes larger than 1). The subcarriers of a groupingmay be associated to the same carrier, e.g. configurably or configuredof predefined. A physical resource block may be consideredrepresentative of a grouping (in frequency domain). A subcarriergrouping may be considered to be associated to a specific channel and/ortype of signaling, its transmission for such channel or signaling isscheduled and/or transmitted and/or intended and/or configured for atleast one, or a plurality, or all subcarriers in the grouping. Suchassociation may be time-dependent, e.g. configured or configurable orpredefined, and/or dynamic or semi-static. The association may bedifferent for different devices, e.g. configured or configurable orpredefined, and/or dynamic or semi-static. Patterns of subcarriergroupings may be considered, which may comprise one or more subcarriergroupings (which may be associated to same or differentsignalings/channels), and/or one or more groupings without associatedsignaling (e.g., as seen from a specific device). An example of apattern is a comb, for which between pairs of groupings associated tothe same signaling/channel there are arranged one or more groupingsassociated to one or more different channels and/or signaling types,and/or one or more groupings without associated channel/signaling).

Example types of signaling comprise signaling of a specificcommunication direction, in particular, uplink signaling, downlinksignaling, sidelink signaling, as well as reference signaling (e.g., SRSor CRS or CSI-RS), communication signaling, control signaling, and/orsignaling associated to a specific channel like PUSCH, PDSCH, PUCCH,PDCCH, PSCCH, PSSCH, etc.).

In this disclosure, for purposes of explanation and not limitation,specific details are set forth (such as particular network functions,processes and signaling steps) in order to provide a thoroughunderstanding of the technique presented herein. It will be apparent toone skilled in the art that the present concepts and aspects may bepracticed in other variants and variants that depart from these specificdetails.

For example, the concepts and variants are partially described in thecontext of Long Term Evolution (LTE) or LTE-Advanced (LTE-A) or NewRadio mobile or wireless communications technologies; however, this doesnot rule out the use of the present concepts and aspects in connectionwith additional or alternative mobile communication technologies such asthe Global System for Mobile Communications (GSM). While describedvariants may pertain to certain Technical Specifications (TSs) of theThird Generation Partnership Project (3GPP), it will be appreciated thatthe present approaches, concepts and aspects could also be realized inconnection with different Performance Management (PM) specifications.

Moreover, those skilled in the art will appreciate that the services,functions and steps explained herein may be implemented using softwarefunctioning in conjunction with a programmed microprocessor, or using anApplication Specific Integrated Circuit (ASIC), a Digital SignalProcessor (DSP), a Field Programmable Gate Array (FPGA) or generalpurpose computer. It will also be appreciated that while the variantsdescribed herein are elucidated in the context of methods and devices,the concepts and aspects presented herein may also be embodied in aprogram product as well as in a system comprising control circuitry,e.g. a computer processor and a memory coupled to the processor, whereinthe memory is encoded with one or more programs or program products thatexecute the services, functions and steps disclosed herein.

It is believed that the advantages of the aspects and variants presentedherein will be fully understood from the foregoing description, and itwill be apparent that various changes may be made in the form,constructions and arrangement of the exemplary aspects thereof withoutdeparting from the scope of the concepts and aspects described herein orwithout sacrificing all of its advantageous effects. The aspectspresented herein can be varied in many ways.

Some useful abbreviations comprise

Abbreviation Explanation ACK/NACK Acknowledgment/NegativeAcknowledgement ARQ Automatic Repeat reQuest CAZAC Constant AmplitudeZero Cross Correlation CBG Code Block Group CDM Code Division MultiplexCM Cubic Metric CQI Channel Quality Information CRC Cyclic RedundancyCheck CRS Common reference signal CSI Channel State Information CSI-RSChannel state information reference signal DAI Downlink AssignmentIndicator DCI Downlink Control Information DFT Discrete FourierTransform DM(-)RS Demodulation reference signal(ing) FDM FrequencyDivision Multiplex HARQ Hybrid Automatic Repeat Request IFFT InverseFast Fourier Transform MBB Mobile Broadband MCS Modulation and CodingScheme MIMO Multiple-input-multiple-output MRC Maximum-ratio combiningMRT Maximum-ratio transmission MU-MIMO Multiusermultiple-input-multiple-output OFDM/A Orthogonal Frequency DivisionMultiplex/Multiple Access PAPR Peak to Average Power Ratio PDCCHPhysical Downlink Control Channel PDSCH Physical Downlink Shared ChannelPRACH Physical Random Access CHannel PRB Physical Resource Block PUCCHPhysical Uplink Control Channel PUSCH Physical Uplink Shared Channel(P)SCCH (Physical) Sidelink Control Channel (P)SSCH (Physical) SidelinkShared Channel RB Resource Block RRC Radio Resource Control SC-FDM/ASingle Carrier Frequency Division Multiplex/Multiple Access SCI SidelinkControl Information SINR Signal-to-interference-plus-noise ratio SIRSignal-to-interference ratio SNR Signal-to-noise-ratio SR SchedulingRequest SRS Sounding Reference Signal(ing) SVD Singular-valuedecomposition TDM Time Division Multiplex UCI Uplink Control InformationUE User Equipment URLLC Ultra Low Latency High Reliability CommunicationVL-MIMO Very-large multiple-input-multiple-output ZF Zero Forcing

Abbreviations may be considered to follow 3G PP usage if applicable.

What is claimed is:
 1. A method of operating a user equipment in a NewRadio, NR, radio access network, the method comprising: receiving a coderate indication that indicates a code rate for feedback controlsignaling, the code rate indication further indicating a mapping betweena number of control information bits I and an anchor frequency resourcestructure to be used for transmitting the feedback control signaling,the anchor frequency resource structure including an anchor resourceblock; and transmitting the feedback control signaling using the anchorfrequency resource structure, the feedback control signalingrepresenting a number I of control information bits of a plurality ofcontrol information types, the I control information bits being encodedwith the code rate.
 2. The method according to claim 1, wherein the coderate indication indicates one of a plurality of code rates possible fora coding scheme.
 3. The method according to claim 1, wherein thefeedback control signaling is transmitted on a physical uplink controlchannel.
 4. The method according to claim 1, wherein the code rateindication indicates one of an upper limit for the code rate and atarget code rate.
 5. The method according to claim 1, wherein the coderate is based on a Physical Uplink Control Channel, PUCCH, format fortransmission of the feedback control signaling.
 6. The method accordingto claim 1, wherein: the I control information bits are encodedaccording to a first encoding scheme if I is not greater than 11 bits;and the I control information bits are encoded according to a secondencoding scheme if I is greater than 11 bits.
 7. A user equipment for aNew Radio, NR, radio access network, the user equipment comprisingprocessing circuitry and being configured to utilize the processingcircuitry to: receive a code rate indication that indicates a code ratefor feedback control signaling, the code rate indication furtherindicating a mapping between a number of control information bits I andan anchor frequency resource structure to be used for transmitting thefeedback control signaling, the anchor frequency resource structureincluding an anchor resource block; and cause transmission of feedbackcontrol signaling using the anchor frequency resource structure thefeedback control signaling representing a number I of controlinformation bits of a plurality of control information types, the Icontrol information bits being encoded with the code rate.
 8. The userequipment according to claim 7, wherein the code rate indicationindicates one of a plurality of code rates possible for a coding scheme.9. The user equipment according to claim 7, wherein the feedback controlsignaling is transmitted on a physical uplink control channel.
 10. Theuser equipment according to claim 7, wherein the code rate indicationindicates one of an upper limit for the code rate and a target coderate.
 11. The user equipment according to claim 7, wherein the code rateis based on a Physical Uplink Control Channel, PUCCH, format fortransmission of the feedback control signaling.
 12. The user equipmentaccording to claim 7, wherein: the I control information bits areencoded according to a first encoding scheme if I is not greater than 11bits; and the I control information bits are encoded according to asecond encoding scheme if I is greater than 11 bits.
 13. A configuringradio node for a New Radio, NR, radio access network, the configuringradio node comprising processing circuitry and being configured toutilize the processing circuitry to: cause transmission of a code rateindication for a user equipment to use for feedback control signaling,the code rate indication indicating a code rate for encoding controlinformation bits of a plurality of control information types of thefeedback control signaling, the code rate indication further indicatinga mapping between a number of control information bits I and an anchorfrequency resource structure to be used for transmitting the feedbackcontrol signaling, the anchor frequency resource structure including ananchor resource block; and receive the feedback control signaling usingthe anchor frequency resource structure, the feedback control signalingrepresenting a number I of control information bits of the plurality ofcontrol information types, the I control information bits being encodedwith the code rate.
 14. The configuring radio node according to claim13, wherein the code rate indication indicates one of a plurality ofcode rates possible for a coding scheme.
 15. The configuring radio nodeaccording to claim 13, wherein the feedback control signaling istransmitted on a physical uplink control channel.
 16. The configuringradio node according to claim 13, wherein the code rate indicationindicates one of an upper limit for the code rate and a target coderate.
 17. The configuring radio node according to claim 13, wherein thecode rate is based on a Physical Uplink Control Channel, PUCCH, formatfor transmission of the feedback control signaling.
 18. The configuringradio node according to claim 13, wherein: the I control informationbits are encoded according to a first encoding scheme if I is notgreater than 11 bits; and the I control information bits are encodedaccording to a second encoding scheme if I is greater than 11 bits.